What

Release 1.5.0 of the bailian-cli family. Bundles the new command groups landed since 1.4.2 (fine-tuning, deployment, datasets, Token Plan, auto-update) together with the composable-package refactor and a new sibling CLI (kscli).

New commands (user-facing)

• bl finetune — model fine-tuning: create / list / get / watch / cancel jobs, training logs, checkpoints, export a checkpoint as a deployable model, query training capability. Types: sft, sft-lora, dpo, dpo-lora, cpt.
• bl deploy — model deployment: create / list / get / update (rate limits) / scale / delete, list deployable models and plans.
• bl dataset — datasets: upload / list / get / delete, plus validate to check a local .jsonl before uploading (ChatML / DPO / CPT).
• bl token-plan — Token Plan management: list seats, add members, batch-assign seats, create per-seat API key.
• Auto-update check — after a command runs, the CLI checks npm (throttled) and shows an Update available hint; a major stable-version gap self-updates. Skipped with --quiet / on bl update.

Architecture (internal)

bailian-cli split into composable packages:

bailian-cli-core       # pure SDK
bailian-cli-runtime    # NEW — CLI framework: createCli, registry, args, output, pipeline
bailian-cli-commands   # NEW — shared command library
bailian-cli            # bl — composes runtime + commands (behavior unchanged)
knowledge-studio-cli   # NEW — kscli, lightweight RAG CLI on the same runtime

Commands declare usageArgs / exampleArgs (no bin prefix) so the runtime renders help per product. Release tooling builds/publishes runtime + commands alongside core + cli.

Version

bailian-cli, bailian-cli-core, bailian-cli-runtime, bailian-cli-commands release in lockstep → all bumped to 1.5.0 (from 1.4.2 / 1.4.0).

knowledge-studio-cli stays at 0.0.1 — it publishes from a separate workflow run and is not in the bailian-cli publish set.

Fixed

• Console gateway commands surface a readable message on a non-string errorCode instead of [object Object].

Notes / follow-ups

• Lockstep validation (tools/release/lib/validate.mjs) requires every package in the publish set to match core's version. The --knowledge publish path includes kscli, so its 0.0.1 would fail that check — decide before the first kscli publish whether kscli joins the 1.5.0 lockstep or the validation exempts it.

Test

• pnpm install --frozen-lockfile ✓ (lockfile unchanged)
• CI: build + vp check + tests

🤖 Generated with Claude Code